翻訳と辞書
Words near each other
・ Comparison of instruction set architectures
・ Comparison of integrated development environments
・ Comparison of Intel processors
・ Comparison of international blood pressure guidelines
・ Comparison of Internet forum software
・ Comparison of Internet Relay Chat bots
・ Comparison of Internet Relay Chat clients
・ Comparison of Internet Relay Chat daemons
・ Comparison of IOC, FIFA, and ISO 3166 country codes
・ Comparison of iOS e-book reader software
・ Comparison of iPod managers
・ Comparison of IPv6 support in operating systems
・ Comparison of iSCSI targets
・ Comparison of Islamic and Jewish dietary laws
・ Comparison of issue-tracking systems
Comparison of Java and Android API
・ Comparison of Java and C++
・ Comparison of Java Remote Desktop projects
・ Comparison of Java virtual machines
・ Comparison of JavaScript charting frameworks
・ Comparison of JavaScript frameworks
・ Comparison of JavaScript-based source code editors
・ Comparison of karate styles
・ Comparison of LAN messengers
・ Comparison of layout engines (Cascading Style Sheets)
・ Comparison of layout engines (Document Object Model)
・ Comparison of layout engines (ECMAScript)
・ Comparison of layout engines (graphics)
・ Comparison of layout engines (HTML)
・ Comparison of layout engines (HTML5 canvas)


Dictionary Lists
翻訳と辞書 辞書検索 [ 開発暫定版 ]
スポンサード リンク

Comparison of Java and Android API : ウィキペディア英語版
Comparison of Java and Android API
This article compares the Java and Android API and virtual machines.
While most Android applications are written in Java-like language, there are many differences between the Java API and the Android API, and Android does not use a Java Virtual Machine but two other ones called either Dalvik or Android Runtime (ART).
There is no Java Virtual Machine in the Android platform. Java bytecode is not executed. Instead Java classes are compiled into a proprietary bytecode format and run on Dalvik, a specialized virtual machine (VM) designed specifically for Android. Unlike Java VMs, which are stack machines, the Dalvik VM is a register-based architecture.
Dalvik has some specific characteristics that differentiate it from other standard VMs:
* The VM was designed to use less space.
* The constant pool has been modified to use only 32-bit indexes to simplify the interpreter.
* Standard Java bytecode executes 8-bit stack instructions. Local variables must be copied to or from the operand stack by separate instructions. Dalvik instead uses its own 16-bit instruction set that works directly on local variables. The local variable is commonly picked by a 4-bit 'virtual register' field.
Because the bytecode loaded by the Dalvik virtual machine is not Java bytecode and due to the specific way Dalvik loads classes, it is not possible to load libraries packages as jar files. A different procedure must be used to load Android libraries, in which the content of the underlying dex file must be copied in the application private internal storage area before it is loaded.
==System properties==
As is the case for the Java SE class , the Android class allows the retrieval of system properties. However, some mandatory properties defined with the Java Virtual Machine have no meaning or a different meaning on Android. For example:
* "java.version" property returns 0 because it is not used on Android,
* "java.specification.version" invariably returns 0.9 independently of the version of Android used,
* "java.class.version" invariably returns 50 independently of the version of Android used,
* "user.dir" has a different meaning on Android,
* "user.home" and "user.name" properties do not exist on Android

抄文引用元・出典: フリー百科事典『 ウィキペディア(Wikipedia)
ウィキペディアで「Comparison of Java and Android API」の詳細全文を読む



スポンサード リンク
翻訳と辞書 : 翻訳のためのインターネットリソース

Copyright(C) kotoba.ne.jp 1997-2016. All Rights Reserved.